Make text data in a database unrecognisable

Make text data in a database unrecognisable

In order to protect sensitive data, text data in a database can be made unrecognisable by a search run.
This task is performed by the cxgosuo.exe utility.
All functions are called via flag /o (like obfuscate) with sub-parameters:

Flag	Task performed	Example	Notes
/o	processes the entire database (i.e. the logical database, which may consist of several physical sub-databases)	processed from segment 2 to the end	recommended for relatively small databases
/osegment s1-s2	processed from segment s1 + 1 to s2 (inclusive)	/osegment 799-1000 Segment 800 to 1000 are processed	for large databases, processing can be carried out in parallel in several sub-processes
/osegment s1	processed from segment s1 + 1 to the end	/osegment 1000 processes the rest
/overify	checks whether all string data has been hidden		Errors are written into the ClassiX logfile, see note on error checking
/overify s1-s2	controlled from segment s1 + 1 to s2 (inclusive)	/overify 799-1000 Segment 800 to 1000 are verified
/overify s1	controlled from segment s1 + 1 to the end	/overify 1000 verifies the rest

Even if the text data themselves are made unrecognisable, these data are still included in the indices.
It is therefore advisable to reduce the indices concerned.

Deactivate affected indexes

• manually select interactively or
• deactivate all string related indices with method DeactivateAll of the Index Manager or
• with method DeactivateSelected of the Index Manager, deactivate all the indices that refer to data fields for which strings have actually been processed.
  A statistic about this is at the end of the log file of the processing.

Notes on error control

All ClassiX objects are iterated in the database for processing.
Verification, on the other hand, iterates over all character strings in the database.
This will include

• the image data of the class CX_BITMAP (for format .bmp BM is always at the beginning, for .jpg the character string exif. → ignore these errors!
• ignore the stream data of all COM objects → Ignore errors in the corresponding segments!
• ignore the compressed bytes of the XML objects (CX_WORD_XML) → Ignore errors in the corresponding segments!

CX_MAX_AS_HANDLING

If problems with the address space occur when processing certain segments, these should be processed separately. If this is still not sufficient, the environment variable CX_MAX_AS_HANDLING can be set to TRUE to activate maximum address space handling.